CVE-2026-32939
DataEase is Vulnerable to H2 JDBC RCE Bypass
Description
DataEase is an open source data visualization analysis tool. Versions 2.10.19 and below have inconsistent Locale handling between the JDBC URL validation logic and the H2 JDBC engine's internal parsing. DataEase uses String.toUpperCase() without specifying an explicit Locale, causing its security checks to rely on the JVM's default runtime locale, while H2 JDBC always normalizes URLs using Locale.ENGLISH. In Turkish locale environments (tr_TR), Java converts the lowercase letter i to İ (dotted capital I) instead of the standard I, so a malicious parameter like iNIT becomes İNIT in DataEase's filter (bypassing its blacklist) while H2 still correctly interprets it as INIT. This discrepancy allows attackers to smuggle dangerous JDBC parameters past DataEase's security validation, and the issue has been confirmed as exploitable in real DataEase deployment scenarios running under affected regional settings. The issue has been fixed in version 2.10.20.
INFO
Published Date :
March 20, 2026, 4:16 a.m.
Last Modified :
March 23, 2026, 7:25 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update DataEase to version 2.10.20.
- Ensure JVM default locale is consistent with H2.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-32939.
| URL | Resource |
|---|---|
| https://github.com/dataease/dataease/commit/8f1c21834a620d37dafb3fa24605c059d0a5b80d | Patch |
| https://github.com/dataease/dataease/releases/tag/v2.10.20 | Product Release Notes |
| https://github.com/dataease/dataease/security/advisories/GHSA-pj7p-3m49-52qq | Exploit Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-32939 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-32939
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-32939 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-32939 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 23, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Added CPE Configuration OR *cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* versions up to (excluding) 2.10.20 Added Reference Type GitHub, Inc.: https://github.com/dataease/dataease/commit/8f1c21834a620d37dafb3fa24605c059d0a5b80d Types: Patch Added Reference Type GitHub, Inc.: https://github.com/dataease/dataease/releases/tag/v2.10.20 Types: Product, Release Notes Added Reference Type GitHub, Inc.: https://github.com/dataease/dataease/security/advisories/GHSA-pj7p-3m49-52qq Types: Exploit, Vendor Advisory -
New CVE Received by [email protected]
Mar. 20, 2026
Action Type Old Value New Value Added Description DataEase is an open source data visualization analysis tool. Versions 2.10.19 and below have inconsistent Locale handling between the JDBC URL validation logic and the H2 JDBC engine's internal parsing. DataEase uses String.toUpperCase() without specifying an explicit Locale, causing its security checks to rely on the JVM's default runtime locale, while H2 JDBC always normalizes URLs using Locale.ENGLISH. In Turkish locale environments (tr_TR), Java converts the lowercase letter i to İ (dotted capital I) instead of the standard I, so a malicious parameter like iNIT becomes İNIT in DataEase's filter (bypassing its blacklist) while H2 still correctly interprets it as INIT. This discrepancy allows attackers to smuggle dangerous JDBC parameters past DataEase's security validation, and the issue has been confirmed as exploitable in real DataEase deployment scenarios running under affected regional settings. The issue has been fixed in version 2.10.20. Added CVSS V4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-178 Added Reference https://github.com/dataease/dataease/commit/8f1c21834a620d37dafb3fa24605c059d0a5b80d Added Reference https://github.com/dataease/dataease/releases/tag/v2.10.20 Added Reference https://github.com/dataease/dataease/security/advisories/GHSA-pj7p-3m49-52qq